[codex] Set Freebuff ad request user agent#661
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Set the Freebuff/Codebuff CLI product
User-Agentheader on ad fetch and impression requests, then forward that header to Carbon ad-serving calls and impression pixel fetches. Carbon still receives the browser-like UA in its requireduseragentquery parameter for targeting, while BuySellAds request logs now seeFreebuff-CLI/<version>instead of the default Node UA. Added a Carbon provider test covering the forwarded header and required query parameter.Validation
Ran Carbon/ZeroClick provider tests, CLI typecheck, web typecheck,
git diff --check, and a liveignore=yesrequest against the public Carbon test zone.